https://ndr-brt.gitlab.io/tags/development/ Recent content in Development on ndr_brt Hugo en made with consciousness Thu, 21 May 2020 14:13:05 +0200 https://ndr-brt.gitlab.io/posts/20200521_future_composition_vertx/ Thu, 21 May 2020 14:13:05 +0200 https://ndr-brt.gitlab.io/posts/20200521_future_composition_vertx/ <p>For those who don&rsquo;t know, Vert.x is an event driven and non blocking application toolkit. It&rsquo;s polyglot, so you can use it with different languages (as <strong>Java</strong>, <strong>Kotlin</strong>, <strong>JavaScript</strong>, <strong>Groovy</strong>, <strong>Ruby</strong> or <strong>Scala</strong>).</p> <h3 id="what-does-non-blocking-mean"> What does &ldquo;non blocking&rdquo; mean? <a class="heading-link" href="#what-does-non-blocking-mean"> <i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"></i> <span class="sr-only">Link to heading</span> </a> </h3> <p>In synchronous programming, when a function is called, the caller has to wait until the result is returned. This behaviour could lead to performance issues.</p> https://ndr-brt.gitlab.io/posts/20200304_zero_downtime_deployment/ Wed, 04 Mar 2020 13:10:48 +0100 https://ndr-brt.gitlab.io/posts/20200304_zero_downtime_deployment/ <p>If you are a software developer that already worked with a production software, for sure you know the struggle:</p> <p><strong>deployment time</strong></p> <p>Hope you already resolved the <em>trust your deployment</em> issue with great practices as Continuous Integration, Automated Testing, Continuous Delivery and so on. Today we&rsquo;ll talk about <strong>zero downtime</strong>.</p> <h2 id="the-problem"> the problem <a class="heading-link" href="#the-problem"> <i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"></i> <span class="sr-only">Link to heading</span> </a> </h2> <p>You already packaged your application into a docker image, published it into a docker registry, started it on your production server with:</p>